Signed-off-by: Lewis Marshall <[email protected]>

Signed-off-by: Lewis Marshall <[email protected]>

Support presence message extras

Release 1.2.43

So that wrapper SDKs like Spaces can use the ErrorInfo class.

Signed-off-by: Lewis Marshall <[email protected]>

Export the ErrorInfo class

[SDK-3805] feat: move react-hooks into ably-js

Release 1.2.44

Cleanup react-hooks dir

* Be consistent with references to React (not react)
* Provide links to Ably docs so that new users arriving here can discover the Ably documentation and understand concepts

Various fixes in React documentation

fix: send ably agent as header in react-hooks time ping

docs: add docs for preventing warnings when used with NextJS

refactor!: remove `AblyProvider` options prop

docs: add array -> object hook return values to react migration guide

fix: throw descriptive error when callbacks used with react

Release 1.2.47

This requires us to now explicitly install the browsers (see [1]).

I’m doing this upgrade not because it’s necessary but because NPM tried
to make it for me when resolving a package-lock.json merge conflict in
an upcoming commit. Given that the upgrade involves this CI change,
thought it best to do it as a separate commit so it doesn’t get lost
inside a merge commit.

[1] https://playwright.dev/docs/release-notes#breaking-changes-playwright-no-longer-downloads-browsers-automatically

…-into-v2

Other than fixing merge conflicts, the notable changes which bring the
recently-added stuff in `main` in line with the changes from v2 are:

- Removing mentions of the `ably/promises` and `Realtime.Promise` API
  from the React hooks code and documentation

- Updating presence message extras test to use the promise-based API

- Fixing a newly-introduced compilation error calling
  `wsConnection.send` in WebSocketTransport (not sure exactly why, but
  I’m guessing something to do with the upgrade to the `ws` library in
  `main` and perhaps some changes to TypeScript version in v2) — the fix,
  which uses a type assertion to always pretend we’re always in the Node
  case, is a bit dodgy but that’s because the signature of
  `ProtocolMessage.serialize` is also a bit dodgy (it refers to Buffer
  even though the code that uses it is also called on web).

The package-lock.json merge conflicts were handled by fixing the
package.json merge conflicts then running `npm install --lockfile-version 2`
using Node 16.20.0. Using Node 18.18.2 seemed to lead to a lockfile that
caused an error "@esbuild/android-arm not accessible from esbuild" when
running `npm ci` in the Node 12 and 14 CI jobs.